|
Story-driven modeling is an Object-oriented modeling technique. Other forms of Object-oriented modeling focus on class diagrams. Class diagrams describe the static structure of a program, i.e. the building blocks of a program and how they relate to each other. Class diagrams also model data structures, but with an emphasis on rather abstract concepts like types and type features. Instead of abstract static structures, story-driven modeling focuses on concrete example scenarios and on how the steps of the example scenarios may be represented as object diagrams and how these object diagrams evolve during scenario execution. == In a nutshell == Story-driven modeling proposes the following software development approach: # Textual scenarios: For the feature you want to implement, develop a textual scenario description for the most common case. Look on only one example at a time. Try to use specific terms and individual names instead of general terms and e.g. role names: #: Scenario Go-Dutch barbecue # *Start: This Sunday Peter, Putri, and Peng meet at the park for a go-Dutch barbecue. They use the Group Account app to do the accounting. # *Step 1: Peter brings the meat for 12$. Peter adds this item to the Group Account app. # *Step 2: Putri brings salad for 9$. Peter adds this item, too. The app shows that by now the average share is 7$ and that Peng still have to bring these 7$ while Peter gets 5$ out and Putri gets 2$ out. # *Step 3: ... # GUI mock-ups: To illustrate the graphical user interface (GUI) for the desired feature, you may add some wireframe models or GUI mock-ups to your scenario: #: Scenario Go-Dutch barbecue # *Start: This Sunday Peter, Putri, and Peng meet at the park for a go-Dutch barbecue. They use the Group Account app to do the accounting. # *Step 1: Peter brings the meat for 12$. Peter adds this item to the Group Account app. # *Step 2: Putri brings salad for 9$. Peter adds this item, too. The app shows that by now the average share is 7$ and that Peng still have to bring these 7$ while Peter gets 5$ out and Putri gets 2$ out: WikipediaGoDutchMockup # *Step 3: ... # Storyboarding: Next, you think about how a certain situation, i.e. a certain step of a scenario may be represented within a computer by a runtime object structure. This is done by adding object diagrams to the scenario. In story driven modeling, a scenario with object diagrams is also called a storyboard. #: Scenario Go-Dutch barbecue # *Start: This Sunday Peter, Putri, and Peng meet at the park for a go-Dutch barbecue. They use the Group Account app to do the accounting. # *Step 1: Peter brings the meat for 12$. Peter adds this item to the Group Account app. # *Step 2: Putri brings salad for 9$. Peter adds this item, too. The app shows that by now the average share is 7$ and that Peng still have to bring these 7$ while Peter gets 5$ out and Putri gets 2$ out: WikipediaGoDutchMockupObject diagram modeling a go-Dutch barbecue # *Step 3: ... # Class diagram derivation: Now it is fairly straight forward to derive a class diagram from the object diagrams used in the storyboards. Class diagram for a go-Dutch barbecue Note, the class diagram serves as a common reference for all object diagrams. This ensures that overall the same types and attributes are used. Using a UML tool, you may generate a first implementation from this class diagram. # Algorithm design: So far you have modeled and implemented that object structures that are deployed in your application. Now you need to add behavior, i.e. algorithms and method bodies. Programming the behavior of an application is a demanding task. To facilitate it, you should first outline the behavior in pseudocode notation. You might do this, e.g. with an object game. For example, to update the saldo attributes of all persons you look at our object structure and from the point of view of the GroupAccount object you do the following: #: Update the saldo of all persons: # * visit each item # * * for each item add the value to the total value and add 1 to the number of items # * compute the average share of each person by dividing the total value by the number of persons # * visit each person # * * for each person reset the saldo # * * for each person visit each item bought by this person # * * * for each item add the value to the saldo of the current person # * * for each person subtract the share from the saldo # Behavior implementation: Once you have refined your algorithm pseudocode down to the level of operations on object structures it is straight forward to derive source code that executes the same operations on your object model implementation. # Testing: Finally, the scenarios may be used to derive automatic JUnit tests. The pseudocode for a test for our example might look like: #: Test update the saldo of all persons: # * create a group account object # * add a person object with name Peter and a person object with name Putri and a person object with name Peng to the group account object # * add an item object with buyer Peter, description Meat, and value 12$ to the group account object # * add an item object with buyer Putri, description Salad, and value 9$ to the group account object # * call method update the saldo of all persons on the group account object # * ensure that the saldo of the Peter object is 5$ # * ensure that the saldo of the Putri object is 2$ # * ensure that the saldo of the Peter object is -7$ # * ensure that the sum of all saldos is 0$ : Such automatic tests ensure that in the example situation the behavior implementation actually does what is outlined in the storyboard. While these tests are pretty simple and may not identify all kinds of bugs, these tests are very useful to document the desired behavior and the usage of the new features and these tests ensure that the corresponding functionality is not lost due to future changes. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Story-driven modeling」の詳細全文を読む スポンサード リンク
|
